Incident resource management

ABSTRACT

In an embodiment, a system may comprise a communications network and processing logic. The processing logic may acquire information regarding an incident, identify a first mobile resource (MR) that may respond to the incident based on a type of the incident and a capability associated with the first MR. The processing logic may further identify a generic path scenario to the incident based on a location of the MR and a location of the incident. The processing logic may identify that the first MR is preferred over a second MR with respect to responding to the incident and assign the first MR to the incident. The processing logic may send a message via the communications network to the first MR to notify the first MR that it has been assigned to the incident.

RELATED APPLICATIONS

This application is a continuation of earlier filed U.S. patentapplication Ser. No. 13/454,581 entitled “INCIDENT RESOURCE MANAGEMENT,”Attorney Docket No. JEC11-01, filed on Apr. 24, 2012 (now allowed),which claims the benefit of U.S. Provisional Patent Application No.61/478,902, titled “Incident Resource Management Systems”, which wasfiled on Apr. 25, 2011 and which the contents thereof are incorporatedby reference in their entirety as though fully set forth herein.

BACKGROUND OF THE INVENTION

The invention generally relates to systems and methods, and morespecifically to incident resource management.

SUMMARY OF THE INVENTION

The following presents a simplified summary of the innovation in orderto provide a basic understanding of some aspects of the invention. Thissummary is not an extensive overview of the invention. It is intended toneither identify key or critical elements of the invention nor delineatethe scope of the invention. Its sole purpose is to present some conceptsof the invention in a simplified form as a prelude to the more detaileddescription that is presented later.

The present invention provides methods and apparatus, including computerprogram products, for incident resource management.

In general, in one aspect, the invention features a system including acommunications network, and processing logic for acquiring informationregarding an incident, the information including a type of the incidentand a location of the incident, identifying a first mobile resource (MR)based on the type of the incident and a capability associated with thefirst MR, identifying a second MR based on the type of the incident anda capability associated with the second MR, identifying a first genericpath scenario to the incident based on a location of the first MR andthe location of the incident, identifying a second generic path scenarioto the incident based on a location of the second MR and the location ofthe incident, identifying the first MR as preferred over the second MRwith respect to responding to the incident, the first MR being deemedpreferred over the second MR based on the first generic path scenarioand the second generic path scenario, and sending a message via thecommunications network to the first MR, the message indicating that thefirst MR is assigned to the incident.

In another aspect, the invention features a method including acquiringinformation regarding an incident, the information including a type ofthe incident and a location of the incident, identifying a first mobileresource (MR) based on the type of the incident and a capabilityassociated with the first MR, identifying a second MR based on the typeof the incident and a capability associated with the second MR,identifying a first generic path scenario to the incident based on alocation of the first MR and the location of the incident, identifying asecond generic path scenario to the incident based on a location of thesecond MR and the location of the incident, identifying the first MR aspreferred over the second MR with respect to responding to the incident,the first MR being deemed preferred over the second MR based on thefirst generic path scenario and the second generic path scenario, andsending a message via a communications network to the first MR, themessage indicating that the first MR is assigned to the incident.

In still another aspect, the invention features a method includingacquiring path information of a mobile resource (MR) via acommunications network, acquiring a location of the MR, determiningbased on the location of the MR and the path information whether the MRhas reached a trigger point; and taking action to accommodate the MRbased on the MR reaching the trigger point.

These and other features and advantages will be apparent from a readingof the following detailed description and a review of the associateddrawings. It is to be understood that both the foregoing generaldescription and the following detailed description are explanatory onlyand are not restrictive of aspects as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate one or more embodiments describedherein and, together with the description, explain these embodiments. Inthe drawings:

FIG. 1 illustrates a block diagram of an example of an incident resourcemanagement system (IRMS);

FIG. 2 illustrates a block diagram of an example of a computing devicethat may included in a command center node (CCN);

FIG. 3 illustrates a block diagram of an example of an incidentdispatcher;

FIG. 4 illustrates a block diagram of an example of a mobile resourcenode (MRN) that may be associated with a mobile resource (MR);

FIG. 5 illustrates a block diagram of an example of a stationaryresource node (SRN) that may be associated with a stationary resource(SR);

FIGS. 6A-D illustrate a flow diagram of example acts that may performedto respond to an incident;

FIGS. 7A-B illustrate a flow diagram of example acts that may beperformed by an MRN;

FIG. 8 illustrates a flow diagram of example acts that may be performedwhile an MR is en route to an incident; and

FIGS. 9A-B illustrate a flow diagram of example acts that may beperformed by an SRN.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. Also, the following detailed description does notlimit the invention.

An incident may involve an occurrence of an event. The event may be ofvarious types. For example, the event may involve an accident (e.g., acar crash, an airplane crash), a visit by a dignitary (e.g., a visit bythe President of the United States), a festival (e.g., Oktoberfest), orother event (e.g., rock concert, sports event, rodeo, convention).

An incident may require various resources to handle the incident. Theseresources may be provided by a government (e.g., city government, stategovernment, federal government) and/or a private entity (e.g., aprivately-owned security service, privately-owned ambulance service).The resources may include, for example, people, equipment, materials, orother resources.

An incident may require specific types of resources. For example, anincident may involve an automobile crash where a person may incurvarious injuries. The injuries may require immediate medical attentionand that the person be transported to a hospital. The incident maywarrant various resources, such as, for example, an ambulance totransport the injured person to the hospital, an emergency medicaltechnician (EMT) to provide immediate medical aid, and a police officerto take a report as well as provide assistance (e.g., traffic control)at the location of the incident. The resources may act as a team thatresponds to the incident. Moreover multiple resources may respond to theincident at the same time. Thus, proper coordination of the resourcesmay be important.

An incident may be time sensitive. For example, the incident may involvean airplane crash and injuries incurred by a person may belife-threatening. Response time of responders to the incident may betime-critical.

An incident may be associated with a location. For example, an incidentmay involve a fire and the location of the incident may be a location ofthe fire.

Time sensitivity, resource requirements, location, and/or type areexamples of characteristics of an incident that may be included ininformation about the incident. Other characteristics, such as, forexample, time-of-day and severity-level, severity of injuries, and/orextent of destruction to property may also be included in informationabout the incident. This information may be used by an incident resourcemanagement system (IRMS) to identify, dispatch, and/or control resourcesto handle the incident.

FIG. 1 illustrates a block diagram of an example of an IRMS 100.Referring to FIG. 1, IRMS 100 may contain various entities includingvarious nodes coupled to a network 120. The nodes may include, forexample, a command center node (CCN) 130, mobile resource nodes (MRNs)400 a-b, terminal node (TN) 170, constraint node (CN) 150, andstationary resource nodes (SRNs) 500 a-b. It should be noted that FIG. 1illustrates an example of an incident resource management system. Anincident resource management system may contain more or fewer entitiesthan the entities shown in FIG. 1. Further, functions associated withthe various entities may be distributed among the entities differentlythan described herein.

A node in IRMS 100 may be associated with an identifier (e.g., anInternet Protocol (IP) address). The identifier may be used to identifythe node in communications that are sent and/or received by the node.For example, CCN 130 may be associated with a first IP address and MRN400 a may be associated with a second IP address. CCN 130 may send amessage to MRN 400 a by specifying the second IP address as adestination address for the message. The message may also include thefirst IP address as a source address so that a source for the messagemay be identified, for example, by MRN 400 a.

CCN 130 may be associated with a command center. CCN 130 may includeprovisions for, inter alia, acquiring information about an incident,identifying one or more resources for the incident, and managing theidentified resources. Managing may include, for example, assigningand/or dispatching the identified resources to the incident. CCN 130 mayinclude a computing device. An example of a computing device that may beincluded in CCN 130 will be described further below.

MRNs 400 a-b may be associated with one or more mobile resources (MRs).An MRN 400 may include logic that may be used to communicate with othernodes in IRMS 100. An example of an MRN will be described further below.

An MR may be assigned and/or dispatched to an incident by, for example,a command center. The MR may be assigned and/or dispatched to theincident based on, for example, information about the incident. Forexample, an incident may involve a house fire and the command center mayidentify a fire engine as an MR that may handle the incident (e.g.,extinguish the fire). The command center may assign and dispatch thefire engine to the incident. Other MRs that may be assigned anddispatched to incidents may include, for example, police cars, taxis,tow trucks, ambulances, aircraft, military equipment, persons (e.g.,police officers, EMTs, military personnel, volunteers), or other mobileresources.

TN 170 may be associated with an endpoint for an incident. For example,an incident may include a car crash involving an injured person. Anendpoint for the incident may be a hospital to where the injured personis to be transported. The hospital may contain a TN 170 thatcommunicates with other nodes in system 100 via network 150. The TN 170may be used to, for example, track an MR along a path taken by the MRfrom the incident to the hospital. Note that a TN 170 may perform otherfunctions for the hospital, such as provide status information about thehospital and/or resources available at the hospital to other nodes inIRMS 100.

CN 150 may include a node that provides constraint information (e.g.,traffic congestion, physical road conditions). The information may beprovided to various nodes in IRMS 100. For example, CCN 130 may identifya path to an incident for an MR. CN 150 may provide information used byCCN 130 to identify the path. Specifically, CN 150 may provide trafficcongestion information to CCN 130. CCN 130 may use the trafficcongestion information to identify the path.

Examples of CNs 150 may include cell phones, sensors, portable computingdevices, tracking devices, and/or location reporting devices. Note thatCN 150 may be fixed or mobile. For example, a CN 150 may be associatedwith a sensor that is located at a fixed location and reports trafficvolume at that location. Likewise, for example, a CN 150 may beassociated with an automobile. The CN 150 may include a locationreporting device that reports a location of the automobile.

SRNs 500 a-b may be associated with stationary (fixed) resources (SRs).Examples of an SR may include a traffic intersection, gate, or bridge.For example, an SR may include an intersection in a path taken by an MRto an incident may be assigned to the incident. Likewise, for example,an SR may include intersections that are not located on the path but mayinfluence traffic patterns in the path.

An SR may be assigned to an incident. For example, if the SR is anintersection in a path taken by an MR to an incident, the SR may beassigned to the incident. Likewise, if the SR may influence trafficpatterns in the path to the incident, the SR may be assigned to theincident.

An SRN 500 associated with an SR may, for example, include logic thatmay report a status of the SR and/or control the SR. For example, an SRmay include an intersection. SRN 500 a may be associated with the SR.The SR may include a traffic light to control the flow of trafficthrough the intersection. SRN 500 a may include logic that may be usedto control and/or report a status of the traffic light. An example of anSRN 500 will be described further below.

Network 120 may be a communications network that may enable messages tobe exchanged between nodes in IRMS 100. The messages may containinformation (e.g., data). The messages may be exchanged using variousprotocols, such as, for example, IP, Asynchronous Transfer Mode (ATM)protocol, Synchronous Optical Network (SONET) protocol, the UserDatagram Protocol (UDP), Transmission Control Protocol (TCP), theInstitute of Electrical and Electronics Engineers (IEEE) 802.11 protocoland/or some other protocol. The messages may be contained in one or moredata packets that may be formatted according to various protocols. Themessages may be unicast, multicast, and/or broadcast to nodes in IRMS100.

Network 120 may include various network devices, such as, for example,gateways, routers, switches, firewalls, servers, repeaters, addresstranslators, and/or other network devices. Portions of the network 120may be wired (e.g., using wired conductors, optical fibers) and/orwireless (e.g., using free-space optical (FSO), radio frequency (RF),acoustic transmission paths). Portions of network 120 may include anopen public network, such as the Internet. Portions of the network 120may include a more restricted network, such as a private intranet,virtual private network (VPN), restricted public service network, and/orsome other restricted network. Portions of network 120 may include awide-area network (WAN), metropolitan area network (MAN), and/or a localarea network (LAN). Portions of network 120 may be broadband, baseband,or some combination thereof. Implementations of network 120 and/ordevices operating in or on network 120 may not be limited with regardsto, for example, information carried by the network 120, protocols usedin the network 120, and/or the architecture/configuration of the network120.

As noted above, CCN 130 may include a computing device. FIG. 2illustrates a block diagram of an example of a computing device 200 thatmay be included in CCN 130. Referring to FIG. 2, computing device 200may include various components, such as, an input-output (I/O) bus 210,processing logic 220, primary storage 230, secondary storage 250, one ormore input devices 260, one or more output devices 270, one or morecommunication interfaces 280, and memory bus 290.

I/O bus 210 may be an interconnect bus that enables communication amongvarious components in computing device 200. These components mayinclude, for example, processing logic 220, secondary storage 250, inputdevices 260, output devices 270, and communication interfaces 280. Thecommunication may include, among other things, transferring information(e.g., control information, data) between the components.

Memory bus 290 may be an interconnect bus that enables information to betransferred between processing logic 220 and primary storage 230. Theinformation may include instructions and/or data that may be executed,manipulated, and/or otherwise processed by processing logic 220. Theinformation may be stored in primary storage 230.

Processing logic 220 may include logic for interpreting, executing,and/or otherwise processing information contained in, for example,primary storage 230 and/or secondary storage 250. Processing logic 220may include a variety of heterogeneous hardware. For example, thehardware may include some combination of one or more processors,microprocessors, field programmable gate arrays (FPGAs), applicationspecific instruction set processors (ASIPs), application specificintegrated circuits (ASICs), complex programmable logic devices (CPLDs),graphics processing units (GPUs), and/or other types of processing logicthat may interpret, execute, manipulate, and/or otherwise process theinformation. Processing logic 220 may comprise a single core or multiplecores. An example of a processor that may be used to implementprocessing logic 220 is the Intel Xeon processor available from IntelCorporation, Santa Clara, Calif.

Secondary storage 250 may include storage that may be accessible toprocessing logic 220 via I/O bus 210. The storage may store informationfor processing logic 220. The information may be executed, interpreted,manipulated, and/or otherwise processed by processing logic 220.Secondary storage 250 may include, for example, one or more storagedevices, such as magnetic disk drives, optical disk drives,random-access memory (RAM) disk drives, flash drives, solid-statedrives, or other storage devices. The information may be stored on oneor more tangible computer-readable media contained in the storagedevices. Examples of tangible computer-readable media that may becontained in the storage devices may include magnetic discs, opticaldiscs, and memory devices (e.g., flash memory devices, static RAM (SRAM)devices, dynamic RAM (DRAM) devices, or other memory devices). Theinformation may include data and/or computer-executable instructions.

Input devices 260 may include one or more devices that may be used toinput information into computing device 200. The devices may include,for example, a keyboard, computer mouse, microphone, camera, trackball,gyroscopic device (e.g., gyroscope), mini-mouse, touch pad, stylus,graphics tablet, touch screen, joystick (isotonic or isometric),pointing stick, accelerometer, palm mouse, foot mouse, puck, eyeballcontrolled device, finger mouse, light pen, light gun, neural device,eye tracking device, steering wheel, yoke, jog dial, space ball,directional pad, dance pad, soap mouse, haptic device, tactile device,neural device, multipoint input device, discrete pointing device, and/orsome other input device. The information may include spatial (e.g.,continuous, multi-dimensional) data that may be input into computingdevice 200 using, for example, a pointing device, such as a computermouse. The information may also include other forms of data, such as,for example, text that may be input using a keyboard.

Output devices 270 may include one or more devices that may outputinformation from computing device 200. The devices may include, forexample, a cathode ray tube (CRT), plasma display device, light-emittingdiode (LED) display device, liquid crystal display (LCD) device, vacuumflorescent display (VFD) device, surface-conduction electron-emitterdisplay (SED) device, field emission display (FED) device, hapticdevice, tactile device, printer, speaker, video projector, volumetricdisplay device, plotter, touch screen, and/or some other output device.Output devices 270 may be directed by, for example, processing logic220, to output the information from computing device 200. Theinformation may be presented (e.g., displayed, printed) by outputdevices 270. The information may include, for example, graphical userinterface (GUI) elements (e.g., windows, widgets, and/or other GUIelements), path and/or status information associated with an MR, statusinformation associated with an SR, text, reports, and/or otherinformation that may be presented by output devices 270.

Communication interfaces 280 may include logic for interfacing commandcenter 200 with, for example, one or more communication networks andenable command center 200 to communicate with one or more entitiescoupled to the communication networks. For example, computing device 200may include a communication interface 280 for interfacing computingdevice 200 to network 120. The communication interface 280 may enablecomputing device 200 to communicate with nodes that may be coupled tonetwork 120, such as SRNs 500 a-b, MRNs 400 a-b, CN 150, and TN 170.Note that computing device 200 may include other communicationinterfaces 280 to connect to other communications networks.

Communication interfaces 280 may include one or more transceiver-likemechanisms that enable computing device 200 to communicate with entities(e.g., nodes) coupled to the communications networks. Examples ofcommunication interfaces 280 may include a built-in network adapter,network interface card (NIC), Personal Computer Memory CardInternational Association (PCMCIA) network card, card bus networkadapter, wireless network adapter, Universal Serial Bus (USB) networkadapter, modem, and/or other device suitable for interfacing computingdevice 200 to a communications network.

Primary storage 230 may include one or more tangible computer-readablemedia that may store information for processing logic 220. Primarystorage 230 may be accessible to processing logic 220 via bus 290. Theinformation may include computer-executable instructions and/or datathat may implement operating system (OS) 132 and incident dispatcher300. The instructions may be executed, interpreted, and/or otherwiseprocessed by processing logic 220.

Primary storage 230 may comprise a RAM that may include one or more RAMdevices for storing information (e.g., data, executable instructions, orother information). The RAM devices may be volatile or non-volatile andmay include, for example, one or more DRAM devices, flash memorydevices, SRAM devices, zero-capacitor RAM (ZRAM) devices, twintransistor RAM (TTRAM) devices, read-only memory (ROM) devices,ferroelectric RAM (FeRAM) devices, magneto-resistive RAM (MRAM) devices,phase change memory RAM (PRAM) devices, or other types of RAM devices.

OS 232 may be a conventional operating system that may implement variousconventional operating system functions that may include, for example,(1) scheduling one or more portions of incident dispatcher 300 to run onthe processing logic 220, (2) managing primary storage 230, and (3)controlling access to various components in command center 200 (e.g.,input devices 260, output devices 270, network interfaces 280, secondarystorage 250) and information received and/or transmitted by thesecomponents. Examples of operating systems that may be used to implementOS 232 may include the Linux operating system, Microsoft Windowsoperating system, the Symbian operating system, Mac OS operating system,and the Android operating system. A distribution of the Linux operatingsystem that may be used is Red Hat Linux available from Red HatCorporation, Raleigh, N.C. Versions of the Microsoft Windows operatingsystem that may be used include Microsoft Windows Mobile, MicrosoftWindows 7, Microsoft Windows Vista, and Microsoft Windows XP operatingsystems available from Microsoft Inc., Redmond, Wash. The Symbianoperating system is available from Accenture PLC, Dublin, Ireland. TheMac OS operating system is available from Apple, Inc., Cupertino, Calif.The Android operating system is available from Google, Inc., Menlo Park,Calif.

It should be noted that computing device 200 is an example of acomputing device that may be included at CCN 130. CCN 130 may includeother computing devices that may have more components or fewercomponents than the components illustrated in FIG. 2. Also, functionsperformed by various components contained in the computing devices maybe distributed among the components differently than as describedherein. Further, functions performed by various components may bedistributed across multiple devices. For example, functions performed byincident dispatcher 300 may be distributed across, for example,client-server devices, mobile devices (e.g., smart phones), and/orvarious data centers.

FIG. 3 illustrates a block diagram of an example embodiment of incidentdispatcher 300. Referring to FIG. 3, incident dispatcher may include anoperational GUI 310 and a dispatcher 330. The operational GUI 310 mayinclude an interface (e.g., a GUI) that may present information aboutresources that may be associated with an incident. The information mayinclude, for example, operational status and/or capabilities associatedwith the resources. Further, the interface may include provisions forpresenting information about one or more incidents that may be handledby the resources.

Resource and incident information may be presented in GUI 310 usingvarious graphical and/or textual affordances, such as icons, text,animation, and/or pictures. For example, MRs may be represented by icons312 a-b, SRs by icons 316 a-b, a constraint node by icon 314, and anincident by icon 318. Note that other ways of presenting the informationmay be provided by GUI 310.

A path that may be taken by a resource (e.g., an MR) assigned to anincident may also be presented in GUI 310 using various graphical and/ortextual affordances. For example, arrows 310 a-c may represent a pathtaken by an MR, represented by icon 312 a, to the incident, representedby icon 318.

GUI 310 may also present a status of a resource and/or incident. Forexample, icon 312 a may be colored a first color to indicate that theMR, represented by icon 312 a, contains various capabilities (e.g., anEMT, defibrillator, oxygen) that may be necessary to respond to theincident. Icon 312 a may be colored a second color to indicate that theMR has been assigned to the incident, represented by icon 318. Further,as the MR travels along the path to the incident, icon 312 a may becolored various colors which represent various statuses of the MR alongthe path. For example, a coloring scheme may be used to indicate aproximity of the MR to the incident or whether the MR has becomedisabled while en route to the incident.

Icons 316 a-b could be presented in various ways to indicate a statusassociated with the SRs represented by the icons. For example, as theMR, represented by icon 312 a, approaches an SR, represented by icon 316a, the SR may change its mode of operation to accommodate the MR. Thischange in mode may be reflected in a presentation of icon 316 a using,for example, coloring, flashing, and/or highlighting.

Dispatcher 330 may include data logic 332, data processor 334, datacollector 336, and data storage 338. Data logic 332 may contain logic(e.g., rules) for processing data that may be collected by the datacollector 336 and/or provided by data storage 338. The logic may define,for example, how data processor 334 interprets the data, processes thedata, and/or presents the data in GUI 310.

Data collector 336 may collect data from various sources. The data maybe used by data processor 334. The data may include information about anincident and/or resources associated with the incident. For example, thedata may include a type of an incident, seriousness of the incident,information about entities (e.g., victims, objects) involved in theincident, resources (e.g., MRs, SRs) assigned to the incident,constraints (e.g. traffic congestion) along paths to the incident,and/or terminals (e.g., hospitals, medical centers, clinics) that may beassociated with the incident.

Data storage 338 may contain data that may also be processed by dataprocessor 334. This information may include, for example, capabilitiesof resources (e.g., whether an MR contains an EMT, whether an SR may becontrolled) that may be assigned to the incident. For example, anincident may involve an accident that requires a victim to betransported to a hospital. Further, the victim's injuries may be suchthat some of them require immediate medical attention. Data storage 338may contain a database that stores information about resources (e.g.,ambulances, EMTs) that may be dispatched to the site of the incident toprovide these requirements.

Data processor 334 may process data collected by data collector 336and/or data contained in data storage 338 according to logic that may bedefined by data logic 332. The processed data may be presented in GUI310. For example, data collector 336 may collect information about anincident. The information may include various characteristics(attributes) associated with the incident, such as a type of incident,number of injuries, severity of injuries, type of property damage, andso on. Based on the collected information and/or information containedin data storage 338, data processor 334 may identify one or more MRsthat could respond to the incident. The MRs may be identified using oneor more rules that may be defined in data logic 332.

Data processor 334 may display various icons in GUI 310 that representthe identified MRs. Data processor 334 may use various schemes (e.g.,text, labeling, coloring, flashing, graphics) to indicate, for example,various characteristics associated with the MRs in GUI 310. For example,data processor 334 may use various schemes to indicate which MRs may begood, better, or best choices for responding to the incident. If a firstMR contains capabilities that meet the requirements for responding tothe incident but may take twenty minutes to reach the scene of theincident, an icon that represents the first MR may be displayed in acolor that indicates “good” in GUI 310, whereas, a second MR thatcontains most but not all of the required capabilities and may take only2 minutes to reach the scene may be displayed in a color that indicates“better” in GUI 310.

Using the GUI 310, a user may select resources to respond to theincident based on, for example, a presentation of icons that mayrepresent the resources. For example, the user may select resourcesbased on colors of the icons representing those resources.

The selections may be collected by data collector 336 and processed bydata processor 334 according to logic that may be defined by data logic332. The processing may include recording the user's selections and adate and time of the selection in data storage 338. Moreover, additionalprocessing may be performed by data processor 334. For example, dataprocessor may assign a selected MR to the incident and identify a paththe MR may take to reach the location of the incident.

FIG. 4 illustrates a block diagram of an example of an MRN 400.Referring to FIG. 4, an MRN 400 may contain various components that mayinclude, for example, a general purpose I/O interface 412, secondarystorage 414, processing logic 416, network interface 420, clock 422,global navigation satellite system (GNSS) receiver (RX) 424, outputinterface 426, input interface 428, network antenna 430, GNSS antenna434, output device 436, and input device 438.

It should be noted that MRN 400 illustrated in FIG. 4 is an example ofan MRN. Other MRNs that contain more components or fewer components thanthe components illustrated in FIG. 4 may be used. In addition, functionsperformed by the various components may be distributed among thecomponents differently than described herein.

General purpose I/O interface 412 may be used to interface the MRN 400with various external devices that may communicate using, for example,various general purpose I/O protocols. These external devices mayinclude, for example, universal serial bus (USB) devices, FireWiredevices (e.g. IEEE 1394 compatible devices), card readers, dongles,and/or other devices.

Secondary storage 414 may be a tangible non-transitory computer-readablemedium that may provide secondary storage for MRN 400. Secondary storage414 may be volatile, non-volatile, or some combination thereof.Secondary storage 414 may be implemented using, for example, disks,solid-state drives, flash memory devices, DRAM, SRAM, and/or otherstorage devices.

Processing logic 416 may include logic for interpreting, executing,and/or otherwise processing information. The information may includecomputer-executable instructions and/or data. The information may alsoinclude information provided by devices coupled to bus 418, such as, forexample, network interface 420, clock 422, GNSS RX 424, output interface426, and input interface 428. The information may be contained in, forexample, (1) memory and/or non-volatile memory that may be part of theprocessing logic 416 and/or (2) secondary storage 414. The memory andnon-volatile memory that may be part of processing logic 416 may be atangible non-transitory computer-readable medium.

Processing logic 416 may include a central processing unit (CPU). TheCPU may include, for example, some combination of one or moreprocessors, microprocessors, field programmable gate arrays (FPGAs),application specific instruction set processors (ASIPs), applicationspecific integrated circuits (ASICs), complex programmable logic devices(CPLDs), GPUs, or other types of processing logic that may interpret,execute, manipulate, and/or otherwise process the information.Processing logic 416 may comprise a single core or multiple cores.

Bus 418 may be an interconnect bus that may enable information (e.g.,data, control information) to be transferred between components that maybe coupled to bus 418. These components may include, for example,general purpose I/O interface 412, secondary storage 414, processinglogic 416, network interface 420, clock 422, GNSS RX 424, outputinterface 426, and input interface 428.

Network interface 420 may include logic for interfacing MRN 400 with,for example, one or more communication networks and enabling MRN 400 tocommunicate with one or more entities (e.g., nodes) coupled to thecommunication networks. For example, network interface 420 may interfaceMRN 400 with network 120 and enable MRN 400 to exchange information withother nodes that may be coupled to network 120, such as CCN 130, otherMRNs 400, SRNs 500, TN 170, and CN 150.

Network interface 420 may include one or more transceiver-likemechanisms that may enable MRN 400 to communicate with entities coupledto the communications networks. The communication may includeinformation that may be provided to processing logic 416 via bus 418.Examples of network interfaces 420 may include a built-in networkadapter, network interface card (NIC), Personal Computer Memory CardInternational Association (PCMCIA) network card, card bus networkadapter, wireless network adapter, Universal Serial Bus (USB) networkadapter, modem, and/or other network interfaces suitable for interfacingMRN 400 to a communications network.

Clock 422 may include logic that may provide time and/or dateinformation to an entity processing logic 416 via bus 418. The timeand/or date information may be based on information that may be providedby an atomic clock service, such as the atomic clock-based date and/ortime provided by the National Institute of Standards and Technology(NIST), Boulder, Colo. The time and/or date information provided by theatomic clock service may be acquired by clock 422 using a receiver thatreceives the information via radio waves (e.g., WWVB), from a server(that may be coupled to the network 120), or otherwise acquired. Itshould be noted that the time and/or date information provided by clock422 may be based on information provided by sources other than an atomicclock service.

GNSS RX 424 may include logic for receiving a GNSS signal andidentifying a location of the MRN 400 based on, for example, thereceived GNSS signal. The location information may be provided toprocessing logic 416 via bus 418. The GNSS signal may be provided by oneor more GNSS satellites 432 that may be part of a GNSS system. Examplesof GNSS systems that may provide the GNSS signal include, for example,the United States Global Positioning System (GPS), Russian GlobalNavigation Satellite System (GLONASS), European Union GalileoPositioning System, Chinese Compass Navigation System, and/or the IndianRegional Navigational Satellite System.

Output interface 426 may include logic for presenting information onoutput device 436. For example, output interface 426 may include logicthat enables text and/or graphics, which may be part of an operationalGUI 440, to be displayed on output device 436. The logic may include aGPU, which may (1) build various display elements (e.g., widgets,graphics) and (2) render the display elements on output device 436.Output device 436 may include one or more devices for presenting theinformation. These devices may include, for example, a CRT, plasmadisplay device, LED display device, LCD device, VFD device, SED device,FED device, touch screen and/or other output device.

Operational GUI 440 may include provisions for displaying, inter alia, astatus of resources associated (e.g., assigned, dispatched) with anincident (e.g., MRs, SRs). For example, operational GUI 440 may containprovisions for displaying locations of MRs that are responding to theincident. MRN 400 may contain provisions to enable a user to specifywhat information may be displayed in operational GUI 440. For example,MRN 400 may contain provisions for displaying resources that areresponding to the event based on the type of resources and/or othercriteria (e.g., MRs that are within a predetermined radius of the MRN400) in operational GUI 440.

Input interface 428 may contain logic for acquiring various inputinformation that may be provided by a user and/or other source. Theinput information may be acquired (read, received) via input device 438.The input information may be made available by input interface 428 viabus 418 to an entity connected to the bus 418, such as processing logic416 and/or output interface 426.

Input device 438 may include one or more devices that may be used toacquire the input information for MRN 400. The devices may include, forexample, a keyboard, computer mouse, microphone, camera, trackball,gyroscopic device (e.g., gyroscope), mini-mouse, touch pad, stylus,graphics tablet, touch screen, joystick (isotonic or isometric), sensors(e.g., temperature sensors, humidity sensors, electronic compass),pointing stick, accelerometer, or other input devices. The acquiredinput information may be transferred from the devices to input interface428.

FIG. 5 illustrates a block diagram of an example of an SRN 500.Referring to FIG. 5, SRN 500 may include various components, such as,for example, a general purpose I/O interface 512, secondary storage 514,processing logic 516, clock 520, network interface 522, controller 524,output interface 526, input interface 528, network antenna 530, externaldevice 532, output device 534, and input device 536.

It should be noted that SRN 500 illustrated in FIG. 5 is an example ofan SRN. Other SRNs that contain more components or fewer components thanthe components illustrated in FIG. 5 may be used. In addition, functionsperformed by the various components may be distributed among thecomponents differently than described herein.

General purpose I/O interface 512 may be used to interface SRN 500 withvarious external devices that may communicate with SRN 500 using variousgeneral purpose I/O protocols. These external devices may include, forexample, universal serial bus (USB) devices, FireWire devices (e.g. IEEE1394 compatible devices), card readers, dongles, and/or other devices.

Secondary storage 514 may be a tangible non-transitory computer-readablemedium that may provide secondary storage for SRN 500. Secondary storage514 may be volatile, non-volatile, or some combination thereof.Secondary storage 514 may include, for example, disks, solid-statedrives, flash memory devices, DRAM, SRAM, and/or other storage devices.

Processing logic 516 may include logic for interpreting, executing,and/or otherwise processing information. The information may includecomputer-executable instructions and/or data. The information may alsoinclude information provided by devices coupled to bus 518, such as, forexample, clock 520, network interface 522, controller 524, outputinterface 526, and input interface 528. The information may be containedin, for example, (1) memory and/or non-volatile memory that may be partof the processing logic 516 and/or (2) secondary storage 514. The memoryand non-volatile memory that may be part of processing logic 516 may bea tangible non-transitory computer-readable medium.

Processing logic 516 may include a central processing unit (CPU). TheCPU may include, for example, some combination of one or moreprocessors, microprocessors, field programmable gate arrays (FPGAs),application specific instruction set processors (ASIPs), applicationspecific integrated circuits (ASICs), complex programmable logic devices(CPLDs), GPUs, or other types of processing logic that may interpret,execute, manipulate, and/or otherwise process the information.Processing logic 516 may comprise a single core or multiple cores.

Bus 518 may be an interconnect bus that may enable information (e.g.,data, control information) to be transferred between components that maybe coupled to bus 518. These components may include, for example,general purpose I/O interface 512, secondary storage 514, processinglogic 516, clock 520, network interface 522, controller 524, outputinterface 526, and input interface 528.

Clock 520 may include logic that may provide time and/or dateinformation to an entity processing logic 516 via bus 518. The timeand/or date information may be based on information that may be providedby an atomic clock service, such as the atomic clock-based date and/ortime provided by the National Institute of Standards and Technology(NIST), Boulder, Colo. The time and/or date information provided by theatomic clock service may be acquired by clock 520 using a receiver thatreceives the information via radio waves (e.g., WWVB), from a server(that may be coupled to the network 120), or otherwise acquired. Itshould be noted that the time and/or date information provided by clock520 may be based on information provided by sources other than an atomicclock service.

Network interface 522 may include logic for interfacing SRN 500 with,for example, one or more communication networks and enabling SRN 500 tocommunicate with one or more entities connected to the communicationnetworks. For example, network interface 522 may interface SRN 500 withnetwork 120 and enable SRN 500 to exchange information with otherentities that may be connected to network 120, such as CCN 130, MRNs400, other SRNs 500, TN 170, and CN 150.

Network interface 522 may include one or more transceiver-likemechanisms that may enable SRN 500 to communicate with entities coupledto the communications networks. The communication may includeinformation that may be provided to processing logic 516 via bus 518.Examples of network interfaces 520 may include a built-in networkadapter, network interface card (NIC), Personal Computer Memory CardInternational Association (PCMCIA) network card, card bus networkadapter, wireless network adapter, Universal Serial Bus (USB) networkadapter, modem, and/or other network interfaces suitable for interfacingSRN 500 to a communications network.

Controller 524 may include logic for controlling one or more externaldevices 532 associated with the SR. Moreover, controller 524 may includelogic for acquiring information about one or more external devices 532associated with the SR.

For example, the SR may be an intersection that is controlled by atraffic light and the controller may be used to control turning on oroff one or more lights associated with the traffic light. The lights maybe turned on or off based on one or more commands that may be sent tothe controller 524 from a component (e.g., processing logic 516) coupledto bus 518. In addition, controller 524 may provide a status of a light.For example, if a light is inoperative (e.g., burned out), controller524 may be able to provide this status. The status may be provided to acomponent coupled to bus 518.

Output interface 526 may include logic for presenting information onoutput device 536. For example, output interface 526 may include logicthat enables text and/or graphics, which may be part of an operationalGUI, to be displayed on output device 536. The logic may include a GPU,which may build various display elements (e.g., widgets, graphics, text,labels) and render the display elements on output device 536. Outputdevice 534 may include one or more devices for presenting theinformation. These devices may include, for example, a CRT, plasmadisplay device, LED display device, LCD device, VFD device, SED device,FED device, touch screen and/or other output device.

Input interface 528 may contain logic for acquiring various inputinformation that may be provided by a user or other source. The inputinformation may be acquired via input device 536. The input informationmay be made available by input interface 528 via bus 518 to an entityconnected to the bus 518, such as processing logic 516 and/or outputinterface 526.

Input device 536 may include one or more devices that may be used toacquire input information for SRN 500. The information may be provided,for example, by a user or other source. The devices may include, forexample, a keyboard, computer mouse, microphone, camera, trackball,gyroscopic device (e.g., gyroscope), mini-mouse, touch pad, stylus,graphics tablet, touch screen, joystick (isotonic or isometric), sensors(e.g., temperature sensors, humidity sensors, electronic compass),pointing stick, accelerometer, and/or other input devices. The acquiredinput information may be transferred to input interface 528.

FIGS. 6A-D illustrate a flow diagram of example acts that may performedto respond to an incident. Acts illustrated in FIGS. 6A-D may beperformed by IRMS 100. Referring to FIG. 6A, at block 610 informationabout an incident may be acquired. The information may be acquired bydata collector 336 from various sources, such as network 120, an MRN400, SRN 500, a 911 operator, and/or other source.

For example, information may be input (e.g., manually, automatically)into CCN 130 (FIG. 1) via an input device 260 (FIG. 2), an MRN 400 (FIG.4) via input device 438, and/or an SRN 500 (FIG. 5) via input device 536and/or external device 532. Information may be transferred to CCN 130via network 120. At CCN 130, data collector 336 may acquire theinformation by reading the information (e.g., from an input device 260),receiving the information (e.g., via the network 120), and/or otherwiseacquiring the information. Data collector 336 may provide the acquiredinformation to data processor 334. The information provided to dataprocessor 334 may be filtered (e.g., prescreened), for example, by datacollector 336.

The information may include various characteristics of the incident,such as type of incident, geographic location of the incident, number ofvehicles involved, number of injuries, severity of injuries, type ofinjuries, types of property damage, extent of property damage, and/orother information that may be associated with the incident.

At block 612 a type of the incident may be identified. The type of theincident may be identified from information acquired at block 610. Forexample, the incident could be a multi-vehicle crash and the acquiredinformation may include a code that identifies the incident as amulti-vehicle crash. The incident type may be identified from the code.

As noted above, the information acquired at block 610 may be acquired bydata collector 336. The information may be provided to the dataprocessor 334 by data collector 336. An incident type may be identifiedby data processor 334 from the acquired information provided by datacollector 336. Data processor 334 may use data logic 332 to identify theincident type from the provided information.

At block 616, one or more MRs may be identified based on, for example,the identified incident type, the acquired information, and/orinformation about one or more capabilities associated with the MRs.Information about capabilities associated with the MRs may be stored indata storage 338. The MRs may be identified by data processor 334 usinginformation provided by the data collector 336 and/or data storage 338,and logic that may be defined by data logic 332.

For example, data collector 336 may acquire information about anincident and provide the information to data processor 334. Dataprocessor 334 may process the information based on one or more rulescontained in data logic 332. Based on this processing, data processor334 may determine that the incident involves injuries that warrant anambulance. Data processor 334 may query data storage 338 for informationrelated to ambulances within a certain radius of a geographic locationof the incident. Data logic 332 may be used by data processor 334 toformulate the query. Moreover, data logic 332 may provide data processor334 with logic for identifying one or more potential ambulances that maybe used to respond to the incident.

At block 618, one or more generic path scenarios may be identified forthe MRs that were identified at block 616. The generic path scenariosmay include paths that may be taken by MRs to the incident. The genericpath scenarios may be used to identify recommended MRs to handle theincident.

The generic path scenarios may be based on various criteria, such as,for example, an expected amount of time that it may take an MR torespond to the incident. The generic path scenarios may take intoconsideration such factors as a geographic location of an MR, history ofcongestion of certain paths, day, time of day, physical road conditions,a geographic location of the incident, and/or other factors. Factorsused to determine the generic path may be identified based on theincident type and/or acquired information.

The generic path scenarios may be identified by, for example, dataprocessor 334 using logic that may be provided by data logic 332 anddata that may be provided by data collector 336 and/or data storage 338.Data used to identify the generic path scenarios may be collected bydata collector 336 from various sources, such as an input device 260,MRN 400, SRN 500, CN 150, and/or other sources.

At block 620, recommended MRs that may respond to the incident may beidentified. The recommended MRs may be identified based on the genericpath scenarios identified at block 618. For example, generic pathscenarios may be analyzed by data processor 334 using logic provided bydata logic 332. The analysis may identify a first group of MRs that mayreach the incident within a certain time window and a second group ofMRs may not reach the incident outside of the time window. Based on thisanalysis, the data processor 334 may identify recommended MRs from thefirst group of MRs.

At block 622 (FIG. 6B), the recommended MRs may be presented. Therecommended MRs may be presented in a display that is provided by anoutput device. For example, after identifying the recommended MRs, dataprocessor 334 may display a list of icons in GUI 310 that indicate whichMRs are recommended. The icons may be displayed on output device 270.

At block 624, a selection of the MRs may be acquired. The selection mayindicate that a first MR is preferred over a second MR with respect toresponding to the incident. The selection may be made, for example,manually (e.g., by a user), automatically (e.g., by data processor 334),or some combination thereof. For example, after displaying icons thatrepresent the recommended MRs, data processor 334 may receive aselection of one or more MRs from a user via an input device 260.

The selection may be based on generic path scenarios for the MRs. Forexample, a first MR may be deemed preferred over a second MR withrespect to responding to the incident based on a generic path scenariofor the first MR and a generic path scenario for the second MR.

At block 626, one or more selected MRs may be assigned to the incident.The MRs may be assigned, for example, manually, automatically, or somecombination thereof. Assignment may involve setting a status of an MR toindicate that the MR has been assigned to the incident. The status maybe set by data processor 334 and maintained in data storage 338.

At block 628, the MRs assigned to the incident may be notified that theyhave been assigned to the incident. Notification may include sending amessage to an MR that indicates the MR is assigned to the incident. Forexample, suppose that an MR associated with MRN 140 a is assigned to anincident. Data processor 334 may generate a message and transfer themessage to the MRN 140 a via network 120. MRN 140 a may receive themessage via network interface 420. Processing logic 416 may process themessage and display a notification (e.g., a popup window) on outputdevice 436 that indicates that the MR has been assigned to the incident.

At block 630, an acceptance of the assignment to the incident may beacquired from the MR. For example, suppose in the above example, thatafter displaying the notification, processing logic 416 receives anindication from a user operating the MRN 140 a that the assignment hasbeen accepted. Processing logic 416 may send a message via networkinterface 420 and network 120 to CCN 130 to indicate that the assignmenthas been accepted. CCN 130 may receive the message from the network 120and data processor 334 may process the received message includingdetermining that the MR has accepted the assignment.

At block 632 (FIG. 6C), updated path information may be generated forthe MRs that have accepted the assignment. The updated path informationmay be based on a generic path scenario that may have been identified atblock 618, updated traffic patterns information, updated weatherinformation, current incident status, updated road conditions, changesin various constraints that may have been used to determine the genericpath information, and/or other information. The information may beacquired from various sources, such as the Internet, MRNs 400, SRNs 500,CNs 150, and/or other sources. The information may be collected by datacollector 336 and processed by data processor 334, which may generatethe updated path information based on the collected data and logicprovided by data logic 332.

At block 634, updated path information may be sent to MRs that haveaccepted the assignment. The updated path information may be sent to theMRNs 400 associated with the MRs in the form of a message that is sentvia network 120. After receiving a message containing the updated pathinformation, an MRN 400 may display the updated path information onoutput device 436.

At block 636, periodic status updates may be acquired from the MRs thathave accepted the assignment and at block 638 a present status of theMRs is updated. For example, an MRN 400 associated with an MR that istraveling to the incident may send messages via network 120 to CCN 130.The messages may contain status information, such as an availability ofthe MR, location of the MR, and/or other status information. CCN 130 mayacquire the messages and process the acquired messages. The messages maybe processed by data processor 334. Data processor 334 may update datastorage 338 based on the status information contained in the message.Moreover, data processor 334 may update GUI 310 to reflect the status ofthe MR.

At 640, an indication that the MRs have reached the location of theincident may be acquired. For example, after reaching the location ofthe incident, an MRN 400 associated with an MR may send a message to CCN130, via network 120, that indicates the MR has reached the location ofthe incident. The CCN 130 may update GUI 310 to indicate that the MR hasreached the location of the incident.

At block 642 (FIG. 6D), a request for additional resources may beacquired. For example, after reaching the location of the incident, aresponder may determine that additional resources are needed to handlethe incident. The responder may send a message via an MRN 400 to CCN 130to request the additional resources. The message may be sent via network120 and received at the CCN 130 via communication interface 280. Theacquired message may be forwarded to data collector 336. Data processor334 may acquire the message from data collector 336 and process themessage. At block 644, the request for additional resources may beprocessed. The request may be processed by data processor 334.Processing may involve identifying additional MRs, such as describedabove.

At block 646, a request may be acquired for a path to a terminal and atblock 648, the request may be processed. For example, a responder mayrequest a path to a hospital via an MRN 400. The request may be sent inthe form of a message that may be sent to CCN 130 via network 120. CCN130 may acquire the request and process it. Processing may includeidentifying a path from the location of the MR to the hospital. The pathmay be identified using information, such as described above. Afteridentifying the path, CCN 130 may transfer the path to the MRN 400 vianetwork 120, as described above. While en route to the terminal, the MRN400 may provide status updates to the CCN 130 and the status updates maybe displayed in GUI 310, such as described above. Further, the terminalmay receive the status updates from the MRN 400 and/or the CCN 120.These updates may be processed by a TN 170 contained at the terminal.Processing may include providing a display of the status of the MR in aGUI at the TN 170.

FIGS. 7A-B illustrate a flow diagram of example acts that may beperformed by an MR. Referring to FIG. 7A, at block 712, an assignment toan incident is received. The assignment may be received in a messagethat is sent to an MRN 400 that is associated with the MR. At block 714,a check is performed to determine whether the assignment has beenaccepted. If the assignment is declined, at block 716, a notification issent to indicate the assignment has been declined. If the assignment isaccepted, at block 718 a notification is sent to indicate that theassignment has been accepted. Either notification may be sent to thesender of the assignment. Further, the notification may be contained ina message that is sent to the sender using the MRN 400.

At block 720 (FIG. 7B), path information to the incident is received.The path information may be received, for example, in a message sent tothe MRN 400. At block 722, the MR proceeds to the incident. The MR mayuse the path information to identify a path to the incident. At block724, the MR arrives at the location of the incident and sends anotification of the MR's arrival. The notification may be contained in amessage that may be sent, for example, to the sender of the assignmentusing the MRN 400.

For example, suppose that CCN 130 receives information about an incidentand determines that an MR should be assigned to the incident. Further,suppose that MRN 400 a is associated with the MR. CCN 130 may generate amessage containing the assignment and send the message to MRN 400 a vianetwork 120. The assignment may be received by MRN 400 a, which mayprocess the message. Processing the message may include displaying anindication of the assignment on output device 436. The indication may bedisplayed in GUI 440 that may be displayed on the output device 436. TheGUI 440 may include provisions (e.g., a widget) to enable a user of theMRN 400 a to indicate whether the assignment is accepted.

Now suppose the user accepts the assignment. The user may indicate thatthey accept the assignment via input device 438. MRN 400 a may generatea message containing the indication and transfer the message ontonetwork 120 via network interface 420. CCN 130 may receive the messageat a communication interface 280. The message may be acquired fromcommunication interface 280 by data collector 336. Data collector 336may transfer the message to data processor 334. Data processor 334 mayprocess the message in accordance with logic that may be defined by datalogic 332. Processing the message may include updating a status of theresource in data storage 338 and displaying an indication in GUI 310that the resource has accepted the assignment.

CCN 130 may generate path information for the MR, such as describedabove. CCN 130 may include the path information in a message that istransferred to the MRN 400 a via network 120. MRN 400 a may receive themessage from the network 120 and process the message. Processing mayinclude displaying the path information on output device 436. MR maythen follow the path to the incident.

After arriving at the incident, MRN 400 a may generate a message thatincludes an indication that the MR has arrived at the location of theincident. MRN 400 a may transfer the message via network 120 to CCN 130.CCN 130 may receive the message from the network 120 and process themessage. Processing may include updating a status of the resource indata storage 338 and displaying an indication in GUI 310 that theresource has arrived at the location of the incident.

Various SRs may be associated with a path that may be identified for anMR. The SRs may be located directly on the path or may be able toinfluence constraints (e.g., for example traffic congestion) associatedwith the path. For example, a first SR associated with a path may beassociated with an intersection is on the path. The intersection maycontain a traffic light that directly controls traffic on the path. Asecond SR associated with an intersection that is not on the path (e.g.,may be a city block away). The intersection associated with the secondSR may contain a traffic light that may be capable of influencing a flowof traffic on the path. For example, the traffic light associated withthe second SR may be capable of controlling traffic that may flow intothe path.

As an MR is en route to an incident, it may approach an SR. The SR mayneed to take action in order to accommodate the MR. For example, an SRmay control an intersection on the path using a traffic light. The MRmay be traveling at a high rate of speed and approaching theintersection. The SR may take action to ensure that the MR may be ableto maintain its high rate of speed through the intersection. The actionmay include controlling the traffic light to ensure the intersection isclear when the MR reaches the intersection.

One way to accommodate an MR at a particular SR may be to monitor thelocation of the MR and when the MR reaches a trigger point, action maybe taken at the SR to accommodate the MR. The trigger point may be alocation along a path, taken by the MR to the incident, where the SR mayneed to take action in order to accommodate the MR. The trigger pointmay be identified based on, for example, a rate of speed of the MR,location of the MR, and/or direction of travel of the MR. Further, theMR and SR may utilize a synchronized time source (e.g., an atomic clockservice) used by both the MR and SR to predict a location of the SR.

For example, an SRN 500 associated with the SR may utilize time and/ordate information provided by clock 520 and information about a lastknown location of the MR (that may be provided by the MR's MRN 400),speed of the MR, and/or other information to predict where the MR may belocated. The SRN 500 may use this predicted location to determine, forexample, whether the MR has reached the trigger point.

After the MR passes the intersection, the SR may no longer need toaccommodate the MR. Here, the SR may be released and return to normaloperation and/or released to accommodate another MR. An SRN 500associated with the SR may determine that the SR is released based on amessage (e.g., a message containing the location of the MR), predictionof the location of the MR, and/or other criteria.

FIG. 8 illustrates a flow diagram of example acts that may be performedwhile an MR is en route to an incident. Referring to FIG. 8, at block812, an MR identifies its geographic location. The location may beidentified by using GNSS RX 424 contained in an MRN 400 that may beassociated with the MR. At block 814, the MR may notify one or more SRsassociated with a path taken by the MR to the incident of the MR'slocation. In addition, the MR may notify a command center that hasdispatched the MR to the incident of the MR's location and/or one ormore constraints that may be on or near the path taken by the MR. A CN150 associated with a constraint may process the notification andprovide an indicator that indicates the MR is within a certain locationof the CN 150. The CN 150 may respond to accommodate the MR. Theindicator may be, for example, a visual indication (e.g., a flashinglight, indication on a display screen), audio indication (e.g., sound),and/or other indication. For example, the CN 150 may provide a visualindication when the MR is within a certain proximity of the CN 150. Thevisual indication may be, for example, a flashing icon that may bedisplayed on a display to notify a person associated with the CN 150 whomay be, for example, hearing impaired.

At block 816, the MR reaches a trigger point for a particular SRassociated with the path. The SR may determine that the MR has reachedthe trigger point by monitoring the MR's location. The SR may takeaction to accommodate the MR and send a notification to the MR that theSR has responded to the MR entering the trigger point. At block 818, theMR receives the notification from the SR that indicates the SR hasresponded to the MR entering the trigger point.

For example, suppose that an MR is associated with MRN 400 a and thatthe MR is dispatched by CCN 130 to an incident. Further, suppose that anSR, on a path taken by the MR to the incident, is associated with SRN500 a. As the MR proceeds along the path, MRN 400 a identifies alocation of the MR. MRN 400 a may identify the location based oninformation provided by GNSS RX 424. MRN 400 a may process theinformation and include an indicator of the location of the MR in amessage. The indicator may include, for example, latitude and longitudeinformation associated with the location of the MR. The MRN 400 a maysend the message via network 120 to SRN 500 a and CCN 130. CCN 130 mayreceive the message and process it. Processing may include updating GUI310 to show the location of the MR indicated in the message.

SRN 500 a may also receive the message and process it. The SRN'sprocessing may include determining where the MR is along the path to theincident and whether the MR has reached a trigger point for the SR basedwhere the MR's location on the path. If it is determined that the MR hasreached the trigger point, the SRN 500 a may enter a mode of operationto accommodate the MR. The SRN 500 a may generate a message thatindicates the SR has determined the MR has reached the trigger point andsend the message to the MR via network 120. MRN 400 a may receive themessage and process it. Processing may include indicating in GUI 440that the SR has responded to the MR entering the trigger point. Notethat SRN 500 a may also send a copy of the message to the CCN 130 andthe CCN 130 may indicate in GUI 310 that the SRN 500 a has responded tothe MR reaching the trigger point.

While en route to an incident, an MR may encounter various constraints(e.g., traffic congestion). Further, these constraints may not becontrollable, for example, by an SR. Here, the MRN 400 associated withthe MR may communicate with a CN 150 to manage the constraint.

For example, suppose the constraint involves a vehicle that is in a pathtaken by an MR. Further, suppose the vehicle contains a CN 150 that iscapable of communicating with an MRN 400 associated with the MR. As theMR approaches the vehicle the MRN 400 may generate and send a message toCN 150 to clear the path (e.g., move over to the side of the road, turnoff to a road not on the path). The CN 150 associated with the vehiclemay receive the message and display an indication that the vehicleshould take action to accommodate the MR. Further the CN 150 may send amessage to the MRN 400 that indicates it has received the notificationand/or taken action to accommodate the MR. Status of the vehicle may bedisplayed in GUI 440.

Note that other ways for determining whether the vehicle has takenaction to accommodate the MR may be used. For example, the CN 150 maysend location information (latitude/longitude) of the vehicle and theMRN 400 may use this information to determine whether the vehicle hasaccommodated the MR. A result of the determination may be displayed inGUI 440 and/or logged at a CCN 130 (e.g., in data storage 338).

FIGS. 9A-B illustrate a flow diagram of example acts that may beperformed by an SRN 500. Referring to FIG. 9A, at block 912 an SRassociated with the SRN 500 may be in normal mode. Normal mode mayinclude, for example, an operational mode the SR operates in provided ithas not been assigned to an incident. For example, the SR may be anintersection that is controlled using a traffic light. When the SR hasnot been assigned to an incident, the traffic light may operate in amode where the light may change from green to red and back to green in 1minute cycles to control the flow of traffic through the intersection.This may be considered a normal mode of operation for the SR. After theSR has been assigned to an incident, the traffic light may operatedifferently.

At block 914, the SR may acquire (1) one or more identifiers for one ormore MRs that are responding to an incident and (2) path information forthose MRs. For a particular MR, an identifier may be an address (e.g.,an IP address) associated with an MRN 400 for the MR. The identifiersand path information for the MRs may be acquired by an SRN 500associated with the SR via a network, such as network 120.

At block 918, the SR acquires location information of an MR. Thelocation information may be contained in a message that may be acquiredby the SRN 500 via network 120, such as described above. At block 920, acheck is performed to determine whether the MR has reached a triggerpoint associated with the SR. If not, the flow returns to block 918.

If the MR has reached the trigger point, at block 922 (FIG. 9B) the SRtakes action to accommodate the MR. For example, as noted above, if theSR is an intersection that contains a traffic light, the SR may use thetraffic light to clear traffic through the intersection. At block 924,the SR acquires location information of the MR. The location informationmay be acquired via an SRN 500 associated with the SR, such as describedabove. At block 926, a check is performed to determine whether the MRhas reached a release point. A release point may be a location on thepath where the SR may be released from accommodating the MR.

At block 928, the SR sends an indication that the MR has reached therelease point. The indication may be sent in a message via the SRN 500associated with the SR, such as described above. The message may be sentto a CCN 130 that dispatched the MR and/or the MRN 400 associated withthe MR. After the MR reaches the release point, the SR may enter anormal mode of operation (block 930) or accommodate another MR if thereare additional MRs to be accommodated by the SR. A normal mode ofoperation may include a mode of operation where the SR is not assignedto an incident.

For example, suppose that CCN 130 dispatches an MR associated with MRN400 a to an incident. Further, suppose that an SR, associated with SRN500 a, is assigned to the incident and is on a path taken by MRN 400 a.CCN 130 may notify SRN 500 a, via network 120, that the SR is assignedto the incident. The CCN 130 may also send information about a pathtaken by the MR and an identifier of the MR to SRN 500 a.

The SR may leave a normal mode of operation and enter a standby mode ofoperation. In standby mode, the SRN 500 a may listen for messages fromMRN 400 a using the identifier. The information may include locationinformation of the MR. Based on the location information, the SRN 500 amay determine that the MR has reached a trigger point. After the SRN 500a has determined that the MR has reached the trigger point, the SRN 500a may take action to accommodate the MR, such as described above.

The MRN 400 a may continue to send location information of the MR viathe network 120 and the SRN 500 a may acquire this location informationby receiving it from the network 120. Based on the received locationinformation, the SRN 500 a may determine that the MR has reached arelease point. After making this determination, the SRN 500 a maygenerate a message indicating that the MR has reached the release point.The SRN 500 a may send the message to the MRN 400 a and the CCN 130. Inaddition, SRN 500 a may place the SR in a normal mode of operation. TheMRN 400 a and the CCN 130 may receive the message and provideindications on output device 436 and GUI 310, respectively.

The foregoing description of embodiments is intended to provideillustration and description, but is not intended to be exhaustive or tolimit the invention to the precise form disclosed. Modifications andvariations are possible in light of the above teachings or may beacquired from practice of the invention. For example, while a series ofacts has been described above with respect to FIGS. 6A-D, 7A-B, 8, and9A-B, the order of the acts may be modified in other implementations.Further, non-dependent acts may be performed in parallel.

Also, the term “user”, as used herein, is intended to be broadlyinterpreted to include, for example, a computing device (e.g., fixedcomputing device, mobile computing device) or a user of a computingdevice, unless otherwise stated.

It will be apparent that one or more embodiments, described herein, maybe implemented in many different forms of software and hardware.Software code and/or specialized hardware used to implement embodimentsdescribed herein is not limiting of the invention. Thus, the operationand behavior of embodiments were described without reference to thespecific software code and/or specialized hardware—it being understoodthat one would be able to design software and/or hardware to implementthe embodiments based on the description herein.

Further, certain features of the invention may be implemented usingcomputer-executable instructions that may be executed by processinglogic, such as processing logic 220, 416, and 516. Thecomputer-executable instructions may be stored on one or more tangiblecomputer-readable storage media. The media may be volatile ornon-volatile and may include, for example, DRAM, SRAM, flash memories,removable disks, non-removable disks, and so on.

No element, act, or instruction used herein should be construed ascritical or essential to the invention unless explicitly described assuch. Also, as used herein, the article “a” is intended to include oneor more items. Where only one item is intended, the term “one” orsimilar language is used. Further, the phrase “based on” is intended tomean “based, at least in part, on” unless explicitly stated otherwise.

It is intended that the invention not be limited to the particularembodiments disclosed above, but that the invention will include any andall particular embodiments and equivalents falling within the scope ofthe following appended claims.

1-21. (canceled)
 22. An incident resource management system, comprising:a command center node (CCN) associated with a command center to acquireinformation of at least one incident event and identify resources toaddress the at least one incident event; one or more mobile resourcenodes (MRNs) that communicate with the CCN to receive one or moremessages from the CCN, wherein the CCN specifies an internet protocol(IP) address for the message; at least one group of mobile resources(MRs) associated with the one or more MRNs, and dispatched to the atleast one incident event by the command center, wherein the at least onegroup of MRs attempt to reach the at least one incident event within atime window; a plurality of distributive nodes and/or stationaryresource nodes (SRNs) to selectively control a flow of traffic through aspecific path of one or more roadway segments, wherein each SRNcommunicates with the other SRNs to selectively control the flow oftraffic through the specific path of the one or more roadway segments,and wherein each distributive node and SRN is networked wired orwirelessly to the CCN, one or more MRNs, at least one group of MRs, andone or more constraint nodes (CNs) to allow communications therebetween;and one or more terminal nodes (TNs) associated with one or moreendpoints for the at least one incident event, wherein the one or moreTNs communicate with the CCN, MRN and the plurality of distributivenodes and track one or more paths of the one or more MRNs from the atleast one incident event to the endpoint for the at least one incidentevent, wherein the one or more roadway segments are digital cuboids andthe events are related to the one or more roadway segments in which theone or more roadway segments control a flow and can extend the flow pastat least one incident location or away from the at least one incidentevent, wherein the CNs, SRNs, and MRNs functional nodes are part of aroadway segment cuboid that communicates with the CCN at a point intime, and wherein the distributed SRNs are also distributive roadwaysegments that functionally control the flow of the MRNs in relation tothe CNs.
 23. The incident resource management system of claim 22,wherein the one or more incident events include a pandemic occurring.24. The incident resource management system of claim 22, wherein thedispatched MRNs include ride-sharing vehicles, and at least onedriverless car is at least one of the CNs.
 25. The incident resourcemanagement system of claim 22, wherein the one or more distributivenodes and/or stationary resource nodes selectively control the follow oftraffic by providing preemptive green lights to one or moreintersections on the specific path of the one or more roadway segments.26. The incident resource management system of claim 22, wherein the oneor more distributive nodes and/or stationary resource nodes selectivelycontrol the flow of traffic during an occurrence of power surges on thepath to the one or more incident events.
 27. The incident resourcemanagement system of claim 22, wherein the one or more distributivenodes and/or stationary resource nodes selectively control the flow oftraffic at each intersection on the path to the one or more incidentevents.
 28. The incident resource management system of claim 27, whereinthe TNs track the one or more paths of the one or more MRs to at leastone pandemic event to the endpoint for the at least one pandemic event.29. The incident resource management system of claim 22, wherein the oneor more distributive nodes selectively control the flow of traffic atone or more intersections experiencing a weather delay on the path tothe one or more incident events.
 30. An incident resource managementsystem, comprising: a command center to dispatch mobile resources (MRNs)to provide assistance based on an incident event occurring at one ormore locations in response to capturing information about the incidentevent occurring, wherein the MRNs include multiple groups of MRNs thatattempt to reach the incident event within a time window; a commandcenter node (CCN) to identify one or more paths of roadway segmentcuboids to the incident event occurring for the MRNs, wherein the CCNidentifies the one or more paths to the incident event based on thecommand center displacing the MRs in response to capturing theinformation about the incident event; a terminal node (TN) to track theMRNs on one or more paths from the incident event to an endpointassociated with the TN, wherein the TN tracks the MRNs based on the CCNidentifying the one or more paths to the incident event; a plurality ofdistributive nodes and/or stationary resource nodes (SRNs) positioned toselectively control a flow of traffic through a specific path of one ormore roadway segments, wherein each SRN communicates with the other SRNsto selectively control the flow of traffic through the specific path ofthe one or more roadway segment cuboids, wherein the pluralitydistributive nodes is positioned to selectively control the flow oftraffic through the specific path of the one or more roadway segmentsbased on the CCN identifying the one or more paths to the incident eventand the TN tracking the MRNs from the one or more paths from theincident event, and wherein each distributive node and/or SRN is networkwired or wirelessly to the command center, MRNs, TN, CCN and one or moreconstraint nodes (CNs); and the one or more CNs that report constraintinformation on the specific path cuboid to the incident event to the TN,the plurality of distributive nodes, and the CCN to enable the TN and/orthe CCN to track the path of the MRNs to the incident event occurring,wherein the one or more CNs report the constraint information on thespecific path to the incident event to the TN based on the plurality ofdistributive nodes selectively controlling the flow of traffic throughthe specific path of the one or more roadway segments, wherein the oneor more roadway segments are digital cuboids and the events are relatedto the one or more roadway segments in which the one or more roadwaysegments control a flow and can extend the flow past at least oneincident location or away from the at least one incident event, whereinthe CNs, SRNs, and MRNs functional nodes are part of a roadway segmentcuboid that communicates with the CCN at a point in time, and whereinthe distributed SRNs are also distributive roadway segments thatfunctionally control the flow of the MRNs in relation to the CNs. 31.The incident resource management system of claim 30, wherein each SRNcommunicates with the other SRNs to selectively control the flow oftraffic through one or more intersections on the specific path of theone or more roadway segments.
 32. The incident resource managementsystem of claim 31, wherein the CCN tracks one or more paths to apandemic condition occurring, and communicates with at least one otherCCN.
 33. The incident resource management system of claim 30, whereinthe dispatched MRNs include ride-sharing vehicles, and at least onedriverless car is at least one of the CNs.
 34. The incident resourcemanagement system of claim 30, wherein the plurality of distributivenodes preempt(s) one or more traffic lights to selectively control theflow of traffic through the specific path of the one or more roadwaysegments.
 35. The incident resource management system of claim 30,wherein the plurality of distributive nodes preempt traffic lights ateach intersection to selectively control the flow of traffic through thespecific path of the one or more roadway segments.
 36. The incidentresource management system of claim 30, wherein the one or more SRNspreempt at least one traffic light during a weather delay event toselectively control the flow of traffic through the specific path of theone or more roadway segments.
 37. The incident resource managementsystem of claim 30, wherein the one or more SRNs preempt traffic lightsduring an occurrence of a pandemic condition to selectively control theflow of traffic on the specific path of the one or more roadwaysegments.
 38. A method comprising: collecting information about anincident event by a data collector and transferring the collectedinformation to a command center node (CCN), wherein the data collectoridentifies a type of incident event that occurred, and includes the typeof incident event in the collected information; identifying one or moremobile resources (MRNs) by a data processor to provide assistance at theincident event, wherein the data processor identifies the one or moreMRNs based on the collected information of the incident event and thetype of incident event that the data collector identified, wherein theone or more MRNs include one or more groups of MRNs that attempt toreach the incident event within a time window; positioning a pluralityof distributive nodes and stationary resource nodes (SRNs) by dataprocessors of the distributive node and the SRNs to selectively controla flow of traffic through a specific path located on one or more roadwaysegments, wherein each SRN communicates with the other SRNs toselectively control the flow of traffic through the specific pathlocated on the one or more roadway segments, wherein the plurality ofdistributive nodes are positioned to selectively control the flow oftraffic through the specific path located on the one or more roadwaysegments according to the data processor identifying the one or moreMRNs to provide the assistance at the incident event, and wherein theplurality of distributive nodes and SRNs are network wired or wirelesslyto the CCN, MRNs, and one or more constraint nodes (CNs) to allowcommunication therebetween; and using one or more path scenarios of theone or more roadway segments by the data processor to identifyrecommended MRNs among the MRNs to address the incident event, whereinthe data processor uses the one or more path scenarios and identifiesthe recommended MRNs based on the data processors of the distributivenodes positioning the plurality of distributive nodes to selectivelycontrol the flow of traffic, wherein the one or more roadway segmentsare digital cuboids and the events are related to the one or moreroadway segments in which the one or more roadway segments control aflow and can extend the flow past at least one incident location or awayfrom the at least one incident event, wherein the CNs, SRNs, and MRNsfunctional nodes are part of a roadway segment cuboid that communicateswith the CCN at a point in time, and wherein the distributed SRNs arealso distributive roadway segments that functionally control the flow ofthe MRNs in relation to the CNs.
 39. The method of claim 38, wherein thedata processor identifies the group of the MRNs that reach the incidentevent within the time window, wherein the time window is based on astationary resource node communicating to at least one of the MRNs andthe CCN in regards to a real-time status of weather delays and/oroccurrences of pandemic conditions in the one or more roadway segments.40. The method of claim 38, further comprising: notifying the CCN of anacceptance of an assignment to the incident event by at least one of therecommended MRNs, wherein the at least one recommended MRN is dispatchedto the incident event, and wherein the incident event includes anoccurrence of a pandemic condition.
 41. The method of claim 38, furthercomprising: providing updated path information to the one or more MRNsin response to weather delays and/or pandemic occurrences on the one ormore roadway segments.